home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
hlp4u2un.zip
/
NET350.ZIP
/
350_POL.DOC
next >
Wrap
Text File
|
1990-09-20
|
9KB
|
215 lines
N E T 3 5 0 G U I D E L I N E S
==================================
F I D O N E T
Net 1:350 - Kitsap Peninsula Gateway Net
Version 1.0
07/03/90
DEFINITIONS:
------------
FIDONET - An international, amateur E-Mail network
ZONE - Collection of Regions over a large geographical area
REGION - Geographical allocation of territory within FidoNet with a
collection of Nets and non-Net Nodes
NET - A coordinated group of Nodes within a Region
HOST (NC)- Net Coordinator; Your source for weekly NODEDIFF files,
FidoNews, NetMail InGate and coordinator of the Net
HUB (NHC)- Net Hub Coordinator, Mini-Host for a portion of the Net
NODE - A FidoNet "member system" listed in the NODELIST
BOSSNODE- A FidoNet Node Hosting a private network of Points
POINT - System not in NODELIST but connected to FidoNet through a
Node
GATEWAY - Inbound/Outbound Node providing services:
IGATE - Inbound NetMail (usually Net Host)
OGATE - Outbound NetMail
ECHO - Coordinator for EchoMail traffic
ZMH - Zone Mail Hour (formerly NMH); 60 minutes set aside for
mail distribution. No BBS users allowed during this time.
EchoMail - Conferenced electronic mail (messages "carbon copied" from
one system to other subscribing systems)
REC - Regional EchoMail Coordinator, IGATE & OGATE for EchoMail
Conferences within the Region
NEC - Net EchoMail Coordinator, IGATE & OGATE for EchoMail
Conferences within the Net
Echo HUB - Local distribution point for EchoMail Conferences
--------------------------
-Geographical assignments:
--------------------------
ZONE 1, REGION 17, NET 350
(usually written 350/xxx.yyy
where xxx is a NODE and yyy is a POINT)
ZONE 1 is assumed if not specified (1:350/xxx.yyy)
-REGION 17 positions:
Regional Coordinator - 17/0
Regional EchoMail Coordinator - (pending)
-NET 350 positions:
HOST (Net Coordinator) - 350/21 (350/0)
ECHO GATEWAY (NEC) - 350/21
Net 350 HUBS: - NetMail EchoMail
BREMERTON 350/0 350/21
POULSBO 350/0 350/21
KITSAP CO. 350/0 350/21
-----------
GUIDELINES:
-----------
This document is an addendum to FidoNet POLICY4.TXT specific to Net
350, Kitsap Peninsula Gateway Net
FidoNet SysOps should read the current FidoNet POLICY4.TXT for general
policies & procedures.
ALL nodes will observe the Zone Mail Hour, 01:00-02:00 PST. This means
that your system will be up and in mail-only mode, (no BBS users or File
Requests allowed). This schedule allows for the following:
01:00 - 02:00 (ZMH) Host system receives NetMmail, FIDONEWS,
NODELIST updates, NODEDIFF, etc.
Systems desiring unlisted NODE numbers are encouraged to operate as
POINTS.
-BOSSNODES - POINTS:
--------------------
A NODE acting as the gateway (BOSSNODE) for a POINT will take whatever
means necessary to hide the POINT's private Net address on outgoing
NetMail and EchoMailL messages and be responsible for the POINT's
behavior (re. FidoNet Policy and Net policy).
The POINT will communicate with FidoNet Nodes via the BOSSNODE only
unless by prior permission of both the BOSSNODE and the receiving
NODE.
-GENERAL INFO:
--------------
All Net 350 Nodes will receive the CHAFF EchoMail Conference from the Net
Host. Restrict access to CHAFF to FidoNet Sysops and Points. ("Read only"
access may be given to others at your discretion.)
The Regional administrative EchoMail Conference (RGN17) is
available from the Echo Hubs. This is a restricted conference.
(Contact the Net Echo Coordinator for current restrictions.)
EchoMail connections outside of Net 350 will be COORDINATED with the
Net EchoMail Coordinator. EchoMail connections outside of the REGION
will be coordinated with the REC and NEC.
NetMail destined for outside Net 350 is sent directly or routed
through the recipient's host.
Commercial traffic, encrypted messages, bombing runs, and EchoMail
should not be routed through any Hubs or Hosts without prior approval
of all Hubs/Hosts involved.
If a Node will be unavailable for mail for more than 24 hours, notify
the Net Host and your EchoMail links. It is especially important to
notify the EchoMail links as they do not have all the space in the
world to hold your mail.
If a Node will be left unattended for a number of days (SysOp's
vacation, trips, etc.), notify your Host and Hub. If the Node has Net
responsibilities such as EchoMail distribution, Hub Coordinator, etc.,
the SysOp will make provisions for access to the Node, during his/her
absence, by someone familiar with that system and provide the Host with
this information.
Nodes will send their Nodelist updates to the Net Coordinator.
Independents will send their Nodelist updates to the Host.
All updates must be received no later than 18:00 Sunday to be
included in the next master nodelist update. Non-approved Nodelist
flags will not be accepted. (See comments in the current
NODEDIFF.###).
Hubs send their Hub-list updates to the Net Host. All updates
must arrive no later than the end of ZMH (02:00 PST) Thursday. The
Host automatically processes the Hub updates and sends the NET-list
update to the Regional Coordinator. Always send a complete Hub-file.
The weekly NODEDIFF.A?? is available on the Net Host system for Net
Independents and distributed to all other Net Nodes directly by the
Net Host.
The weekly FNEWS is available to Net Independents and distributed to
the Hub Coordinators for distribution to the other Nodes.
-COMPLAINTS & PROBLEMS:
-----------------------
Polite, informal discussion of problems at the Net level (Node to Node,
*C to *C) is the best first step toward the resolution of most Net 350
problems. If that procedure fails to solve a problem, discuss it with
your coordinator. If a resolution is not found by this means, a
formal complaint may be issued via NetMail to your Net Coordinator.
Fidonet POLICY4.TXT defines procedures from this point. Problems with
Nodes outside of Net 350 should be discussed with your Net Host who
will work through the offending Node's Host to resolve the problem.
===============
APPLICATIONS FOR NEW FIDONET NODES:
-----------------------------------
System Operators (SysOps) wishing to apply for a Node Number in
Net 350 will:
Use FidoNet compatible software.
Read the current FidoNet POLICY4.TXT, NEWSYSOP.TXT, 350_POL.TXT and be
prepared to comply with these documents.
Have a current, compiled Nodelist (Nodelists, Nodediffs, and
processing utilities are available on the Host system and on most other
FidoNet Systems).
Complete the Net 350 application (APPLY350) and send copies (via
NetMail) to the Net Host and to the appropriate Hub Coordinator.
Be prepared to receive a Netmail response from the Hub Coordinator.
Hub Coordinators will issue Node Numbers and apprise the applicant of
the date of his/her inclusion in the Nodelist.
After receiving the NODEDIFF (from the Net Host) and successfully
processing a current, useable Nodelist, new Nodes may contact the Net
EchoMail Coordinator (via NetMail) for instructions regarding EchoMail
conference connections. If you are unable to contact the NEC, contact
the appropriate Echo Hub.
Modified by:
Jim Barth, Net Co-ordinator, 1:350/0 (Kitsap Peninsula Gateway Net)
07/03/90
Liberally plagiarized from 138-POL.TXT, courtesy of Ron Amos